Demo will be published at https://apps.inindca.com/common-ui-docs/genesys-webcomponents/feature/COMUI-1736

LGTM but I think worth bringing up the questions you have with the team

I was just reading up on how the start and end would work if you were crossing over midnight for example if you have a min of 22:00 and an end of 04:00. Apparently for the native timepicker it wraps around midnight . So it would,

• The valid time range would start at 22:00 (10:00 PM) and continue until 23:59 (11:59 PM).
• Then, it wraps around midnight, continuing from 00:00 (12:00 AM) to 04:00 (4:00 AM).

Still uncertain how it works in terms of wrapping around midnight but I think you could potentially create a validation function .I think it might be possible to convert the start and end times into a comparable format like seconds from midnight. You could then check If min is less than max check if the time value falls between min and max so eg

value = 01:00 , start = 22:00 , end = 04:00

if ( 22:00 < 04:00 ) then
// no wrap around
      return 1:00 >= 22:00 && 1:00 <= 04:00 
else
//wrap around
    return 1:00 >= 22:00 || 1:00 <= 04:00

so this should return true. This is just a rough idea of what I was thinking about but not sure if we want to be thinking about the crossover.

I was just reading up on how the start and end would work if you were crossing over midnight for example if you have a min of 22:00 and an end of 04:00. Apparently for the native timepicker it wraps around midnight . So it would,

* The valid time range would start at 22:00 (10:00 PM) and continue until 23:59 (11:59 PM).

* Then, it wraps around midnight, continuing from 00:00 (12:00 AM) to 04:00 (4:00 AM).

Still uncertain how it works in terms of wrapping around midnight but I think you could potentially create a validation function .I think it might be possible to convert the start and end times into a comparable format like seconds from midnight. You could then check If min is less than max check if the time value falls between min and max so eg

value = 01:00 , start = 22:00 , end = 04:00

if ( 22:00 < 04:00 ) then
// no wrap around
      return 1:00 >= 22:00 && 1:00 <= 04:00 
else
//wrap around
    return 1:00 >= 22:00 || 1:00 <= 04:00

so this should return true. This is just a rough idea of what I was thinking about but not sure if we want to be thinking about the crossover.

@gavin-everett-genesys This is ready for review again. Thanks!

Should min and max work with the 12 hour format as well? Pressing the AM/PM button allows for selecting "out of bounds" times in 12 hour format mode

Should min and max work with the 12 hour format as well? Pressing the AM/PM button allows for selecting "out of bounds" times in 12 hour format mode

@daragh-king-genesys I think you had mentioned we should not do the min and max for the 12 hour format but correct me if I'm wrong.

Should min and max work with the 12 hour format as well? Pressing the AM/PM button allows for selecting "out of bounds" times in 12 hour format mode

@daragh-king-genesys I think you had mentioned we should not do the min and max for the 12 hour format but correct me if I'm wrong.

If it is the case that 12 hour format is not supported I would suggest the following

1. do a check like if format is not 12hour and there is min / max prop then use the min max prop logic, otherwise ignore it
2. perhaps consider logWarn if the format is 12hr and there is min/max prop added